Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1526

reference
243-tree-1
name
1526
tree-preservation-order

undefined

243-tpo-1
uprn
address-text
point
POINT (-1.005101 50.854005)
geometry
MULTIPOLYGON (((-1.005045 50.853999,-1.005047 50.854010,-1.005055 50.854021,-1.005067 50.854029,-1.005083 50.854034,-1.005101 50.854036,-1.005118 50.854034,-1.005134 50.854029,-1.005147 50.854021,-1.005155 50.854011,-1.005158 50.854000,-1.005156 50.853989,-1.005148 50.853979,-1.005136 50.853971,-1.005120 50.853966,-1.005102 50.853964,-1.005085 50.853965,-1.005069 50.853970,-1.005056 50.853978,-1.005048 50.853988,-1.005045 50.853999)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL